Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21dc66dbfbf8ebfbf241dcd689d0a23f711da8da8b4215781255a457788fb808

Tx prefix hash: 44e1729d4e9cb8aa2d28fd22a33499d151621ea2d3ce877f7a700e21154921f6
Tx public key: 99019c5c3a83a1fa1fa5b61fcce99b67f3e3bcca9461aace7fea869ee4807f1c
Timestamp: 1740816096 Timestamp [UCT]: 2025-03-01 08:01:36 Age [y:d:h:m:s]: 00:264:23:24:15
Block: 1229665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187126 RingCT/type: yes/0
Extra: 0199019c5c3a83a1fa1fa5b61fcce99b67f3e3bcca9461aace7fea869ee4807f1c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 986ec6ba0a0b35a8715cd31e9ee957096761c65351f28c62aeb53a778d23eab6 0.600000000000 1716552 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": 1229675, "vin": [ { "gen": { "height": 1229665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "986ec6ba0a0b35a8715cd31e9ee957096761c65351f28c62aeb53a778d23eab6" } } ], "extra": [ 1, 153, 1, 156, 92, 58, 131, 161, 250, 31, 165, 182, 31, 204, 233, 155, 103, 243, 227, 188, 202, 148, 97, 170, 206, 127, 234, 134, 158, 228, 128, 127, 28, 2, 17, 0, 0, 0, 3, 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