Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f57d2e37ca7dd5c8e931293835022e7ac97e79985af07ef062b8baeb76e2a5a

Tx prefix hash: a140d48c13764efcefcc9cb1f0654f76df4dc0baa4ec632ee27093e69f61a1d1
Tx public key: ce4260f6a59c801ff46088b5cfc5f3791bb8b88c9bf2641518f36948d8a9a458
Timestamp: 1717184135 Timestamp [UCT]: 2024-05-31 19:35:35 Age [y:d:h:m:s]: 00:225:04:29:16
Block: 1034217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161151 RingCT/type: yes/0
Extra: 01ce4260f6a59c801ff46088b5cfc5f3791bb8b88c9bf2641518f36948d8a9a4580211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b583737dcbfdd987aaf92d25482d9a402ccf87332c8c3715c6597e866cbf5086 0.600000000000 1502708 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": 1034227, "vin": [ { "gen": { "height": 1034217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b583737dcbfdd987aaf92d25482d9a402ccf87332c8c3715c6597e866cbf5086" } } ], "extra": [ 1, 206, 66, 96, 246, 165, 156, 128, 31, 244, 96, 136, 181, 207, 197, 243, 121, 27, 184, 184, 140, 155, 242, 100, 21, 24, 243, 105, 72, 216, 169, 164, 88, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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