Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aee8e022e65f5e0a1eee08f267c63f335a557e045adf4abef96b8b284deb2ef

Tx prefix hash: dc073e7432587567eb8a343fca59b9305cf362df8171e9e51403eeda8bf9eeef
Tx public key: aa65602d10516d084fd15bd163de34122c1fdad54e2810b8bf7f51ddd0f80047
Timestamp: 1737162026 Timestamp [UCT]: 2025-01-18 01:00:26 Age [y:d:h:m:s]: 00:058:10:14:10
Block: 1199681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41555 RingCT/type: yes/0
Extra: 01aa65602d10516d084fd15bd163de34122c1fdad54e2810b8bf7f51ddd0f80047021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 078c5b48c30724a564dc1b24287d64457cf8e1c69868b0db42f095b1855bc2a0 0.600000000000 1686314 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": 1199691, "vin": [ { "gen": { "height": 1199681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "078c5b48c30724a564dc1b24287d64457cf8e1c69868b0db42f095b1855bc2a0" } } ], "extra": [ 1, 170, 101, 96, 45, 16, 81, 109, 8, 79, 209, 91, 209, 99, 222, 52, 18, 44, 31, 218, 213, 78, 40, 16, 184, 191, 127, 81, 221, 208, 248, 0, 71, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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