Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d3426a6157910975bf0a3a4eccb8b20170509a7d240987df161cb8d8b9278d

Tx prefix hash: 39d3946ce9497ce2affae516270a504fe4eb2f8e217ec5481a1bc78968d9ba61
Tx public key: a104aa8cbfa4a9ae3a37244bd4c0f3719544594e1ccf2fa13d71ea400231688e
Timestamp: 1738523261 Timestamp [UCT]: 2025-02-02 19:07:41 Age [y:d:h:m:s]: 00:358:20:10:20
Block: 1210685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254152 RingCT/type: yes/0
Extra: 01a104aa8cbfa4a9ae3a37244bd4c0f3719544594e1ccf2fa13d71ea400231688e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cdb2074a6ba350930000701d2d97f2a9b5c4563f035fa029a85834c44279a0a 0.600000000000 1697438 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": 1210695, "vin": [ { "gen": { "height": 1210685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cdb2074a6ba350930000701d2d97f2a9b5c4563f035fa029a85834c44279a0a" } } ], "extra": [ 1, 161, 4, 170, 140, 191, 164, 169, 174, 58, 55, 36, 75, 212, 192, 243, 113, 149, 68, 89, 78, 28, 207, 47, 161, 61, 113, 234, 64, 2, 49, 104, 142, 2, 17, 0, 0, 0, 1, 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