Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0d76bfa64f122fcc6efc856b53b9ac53f813c0ed40e25f2bac37c4580df1cbc

Tx prefix hash: ca20194d64217313d715f0a8bcc12bec7403710be173a870d0b1a6a1b33d236d
Tx public key: 7754433c3ab8c2c382de0631595fced645102df0448daaac409c7f91832a0326
Timestamp: 1733064316 Timestamp [UCT]: 2024-12-01 14:45:16 Age [y:d:h:m:s]: 00:125:13:02:54
Block: 1165766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89526 RingCT/type: yes/0
Extra: 017754433c3ab8c2c382de0631595fced645102df0448daaac409c7f91832a03260211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9c56fee83e06a0c7b9a2de598e90426b8b58a13594167b72c5263971ef7fc0d 0.600000000000 1651441 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": 1165776, "vin": [ { "gen": { "height": 1165766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9c56fee83e06a0c7b9a2de598e90426b8b58a13594167b72c5263971ef7fc0d" } } ], "extra": [ 1, 119, 84, 67, 60, 58, 184, 194, 195, 130, 222, 6, 49, 89, 95, 206, 214, 69, 16, 45, 240, 68, 141, 170, 172, 64, 156, 127, 145, 131, 42, 3, 38, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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