Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1742b85a92f421b359bb5d0b10945a2bcc864ff7b3f53ddcb475516ac91e987a

Tx prefix hash: 0ce0dadbd982edcc805f3601e686eee0a412cb4d8015f55caabc4eb8f930a4af
Tx public key: 8284f0a3966e83aa716eecfcbc284ec24eb8875f64e23d65f2516f24f360f698
Timestamp: 1721348172 Timestamp [UCT]: 2024-07-19 00:16:12 Age [y:d:h:m:s]: 00:308:22:56:22
Block: 1068749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220754 RingCT/type: yes/0
Extra: 018284f0a3966e83aa716eecfcbc284ec24eb8875f64e23d65f2516f24f360f698021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2f5c3fca5fceb9cf6887ea186b1293e399f37da86b8d0d291d9531fc473df22 0.600000000000 1539898 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": 1068759, "vin": [ { "gen": { "height": 1068749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2f5c3fca5fceb9cf6887ea186b1293e399f37da86b8d0d291d9531fc473df22" } } ], "extra": [ 1, 130, 132, 240, 163, 150, 110, 131, 170, 113, 110, 236, 252, 188, 40, 78, 194, 78, 184, 135, 95, 100, 226, 61, 101, 242, 81, 111, 36, 243, 96, 246, 152, 2, 17, 0, 0, 0, 7, 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