Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59ff25fe6246ac79f4d36bc5ca64257bd656d5d809d4cd26d626783d77beb345

Tx prefix hash: 2532fbd857431d67bd265cfb5eba9413fad4121f68c279216d5a385a0b4faff8
Tx public key: fbcc363ef3a9eebbe2f0a0b7d9e35dfb2a04ab2782cbd5632e497248d82c2f51
Timestamp: 1743991144 Timestamp [UCT]: 2025-04-07 01:59:04 Age [y:d:h:m:s]: 00:228:02:19:00
Block: 1255941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160757 RingCT/type: yes/0
Extra: 01fbcc363ef3a9eebbe2f0a0b7d9e35dfb2a04ab2782cbd5632e497248d82c2f510211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c281793095a3d6d014f0908d06e0521a3f9547a3cef925814d6595649d4f1eab 0.600000000000 1743048 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": 1255951, "vin": [ { "gen": { "height": 1255941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c281793095a3d6d014f0908d06e0521a3f9547a3cef925814d6595649d4f1eab" } } ], "extra": [ 1, 251, 204, 54, 62, 243, 169, 238, 187, 226, 240, 160, 183, 217, 227, 93, 251, 42, 4, 171, 39, 130, 203, 213, 99, 46, 73, 114, 72, 216, 44, 47, 81, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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