Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1d306f9a8e8b849ca79829c8e09701d72453a938d96deb6122caa5e79e5022ef

Tx prefix hash: f250894a9b4331bc3a8e37559a9c83c017307fe288a74fe94838251902ae1e11
Tx public key: ed7f1a164ee1aef20e66541e924fc7ce5230dcaef0e9531947a60d6d711fc563
Timestamp: 1727203795 Timestamp [UCT]: 2024-09-24 18:49:55 Age [y:d:h:m:s]: 01:045:02:50:48
Block: 1117279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290640 RingCT/type: yes/0
Extra: 01ed7f1a164ee1aef20e66541e924fc7ce5230dcaef0e9531947a60d6d711fc563021100000002e914dd15000000000000000000

1 output(s) for total of 0.608020000000 dcy

stealth address amount amount idx
00: 2b5bcc5d0d18bcb3cb1cd7e005662ff2970484a70c4ed4aa3fdbebc0baadbd1a 0.608020000000 1598056 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1117289, "vin": [ { "gen": { "height": 1117279 } } ], "vout": [ { "amount": 608020000, "target": { "key": "2b5bcc5d0d18bcb3cb1cd7e005662ff2970484a70c4ed4aa3fdbebc0baadbd1a" } } ], "extra": [ 1, 237, 127, 26, 22, 78, 225, 174, 242, 14, 102, 84, 30, 146, 79, 199, 206, 82, 48, 220, 174, 240, 233, 83, 25, 71, 166, 13, 109, 113, 31, 197, 99, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8