Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4445ef0947ebce53c69a33d387c54b64c5ffdd0be453f747a2cbca9d64941113

Tx prefix hash: c284713fa3777a01bf4a33d82ad835fb37c34ad2084319dfe425041335ae8192
Tx public key: 9a9e0f6e16c3d2f6b212b14dfa080d6e7e86b1041fd0a3d330fd48a5ff540613
Timestamp: 1712583615 Timestamp [UCT]: 2024-04-08 13:40:15 Age [y:d:h:m:s]: 00:342:21:34:21
Block: 996044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245191 RingCT/type: yes/0
Extra: 019a9e0f6e16c3d2f6b212b14dfa080d6e7e86b1041fd0a3d330fd48a5ff5406130211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1208ce97183e15dade365d23e7fcd5f990b9e2c97c78718fbf28d03b5a82ae8 0.600000000000 1456460 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": 996054, "vin": [ { "gen": { "height": 996044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1208ce97183e15dade365d23e7fcd5f990b9e2c97c78718fbf28d03b5a82ae8" } } ], "extra": [ 1, 154, 158, 15, 110, 22, 195, 210, 246, 178, 18, 177, 77, 250, 8, 13, 110, 126, 134, 177, 4, 31, 208, 163, 211, 48, 253, 72, 165, 255, 84, 6, 19, 2, 17, 0, 0, 0, 1, 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