Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df4536443fe83f94948e35a2c997ed0d67543dcc80b6f02b5a753b8304056e43

Tx prefix hash: 8e0481694eacd25feb87eafb343dfadf375e907206d7be050a6a47612c7b30f5
Tx public key: 06a4c2230729209a8e1f2785fe9f2ae1465b0438027e8c3533e5eea11f178cc2
Timestamp: 1721268226 Timestamp [UCT]: 2024-07-18 02:03:46 Age [y:d:h:m:s]: 00:129:16:59:50
Block: 1068084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92797 RingCT/type: yes/0
Extra: 0106a4c2230729209a8e1f2785fe9f2ae1465b0438027e8c3533e5eea11f178cc202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c24bd4a08f7857d1c815bb0ed9c81c181edefecd217feafa7efffae77344c907 0.600000000000 1539091 of 15

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": 1068094, "vin": [ { "gen": { "height": 1068084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c24bd4a08f7857d1c815bb0ed9c81c181edefecd217feafa7efffae77344c907" } } ], "extra": [ 1, 6, 164, 194, 35, 7, 41, 32, 154, 142, 31, 39, 133, 254, 159, 42, 225, 70, 91, 4, 56, 2, 126, 140, 53, 51, 229, 238, 161, 31, 23, 140, 194, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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