Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8103b5215ed0b92ed190628a005cb8295c30b4ab0aeae6a04db4e85bccd1677

Tx prefix hash: 76ef50f7dd8caa9efbdab700bc875fa3f2d596ae67532c2b8c35fc2d4196dd1a
Tx public key: 10395ad54a32784e0bebba0cd2a8aac2a2f173a206a567724ea8832c0e10418b
Timestamp: 1717887330 Timestamp [UCT]: 2024-06-08 22:55:30 Age [y:d:h:m:s]: 00:283:19:08:05
Block: 1040048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202817 RingCT/type: yes/0
Extra: 0110395ad54a32784e0bebba0cd2a8aac2a2f173a206a567724ea8832c0e10418b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e31ae56a29a5a79b0704982776df619be451cc8d9bd2b850aa5c4326fe79ed42 0.600000000000 1508703 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": 1040058, "vin": [ { "gen": { "height": 1040048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e31ae56a29a5a79b0704982776df619be451cc8d9bd2b850aa5c4326fe79ed42" } } ], "extra": [ 1, 16, 57, 90, 213, 74, 50, 120, 78, 11, 235, 186, 12, 210, 168, 170, 194, 162, 241, 115, 162, 6, 165, 103, 114, 78, 168, 131, 44, 14, 16, 65, 139, 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