Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb8ba64386736e72eddc1d9e8d42ced5a0b3b626dcef75c0073e6cde6f764591

Tx prefix hash: 4a4bc0588277b6aeec7e1d13fafd3722c54ce13ce56fae6046a021de5041da63
Tx public key: 44392a977c015bf49eb868ddc1300145f4fe0bddc4e8734421c7abd23e5a1c5e
Timestamp: 1749504652 Timestamp [UCT]: 2025-06-09 21:30:52 Age [y:d:h:m:s]: 00:153:20:23:38
Block: 1301617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107622 RingCT/type: yes/0
Extra: 0144392a977c015bf49eb868ddc1300145f4fe0bddc4e8734421c7abd23e5a1c5e02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d98e8c53f7e91ed20516e68a0694d0cdde5d297c5a2d77d2abf62391ad1e545b 0.600000000000 1789178 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": 1301627, "vin": [ { "gen": { "height": 1301617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d98e8c53f7e91ed20516e68a0694d0cdde5d297c5a2d77d2abf62391ad1e545b" } } ], "extra": [ 1, 68, 57, 42, 151, 124, 1, 91, 244, 158, 184, 104, 221, 193, 48, 1, 69, 244, 254, 11, 221, 196, 232, 115, 68, 33, 199, 171, 210, 62, 90, 28, 94, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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