Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb9e817bbe8f6e8638baa0d49040f2ba9233b053028f5ff3722e5a77fd573c1c

Tx prefix hash: 21d0b6c513fd7c263aafddc610bc837de74350b6e285f4a6e342483358fe0989
Tx public key: 6abe2891b7364ef2bab31501f144a84bfe327816c7792178efb1c5a5e94c50e2
Timestamp: 1716180192 Timestamp [UCT]: 2024-05-20 04:43:12 Age [y:d:h:m:s]: 01:027:19:23:34
Block: 1025895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280684 RingCT/type: yes/0
Extra: 016abe2891b7364ef2bab31501f144a84bfe327816c7792178efb1c5a5e94c50e2021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03db9ddbe00a2a6376d4a63735424a499fdfccc664223dcd023a8d2bf8a6ea2d 0.600000000000 1492678 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": 1025905, "vin": [ { "gen": { "height": 1025895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03db9ddbe00a2a6376d4a63735424a499fdfccc664223dcd023a8d2bf8a6ea2d" } } ], "extra": [ 1, 106, 190, 40, 145, 183, 54, 78, 242, 186, 179, 21, 1, 241, 68, 168, 75, 254, 50, 120, 22, 199, 121, 33, 120, 239, 177, 197, 165, 233, 76, 80, 226, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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