Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5c09b009082b926c2c4aaeb0043dec35b18237a84a92e1ab3e704e1a5e98a22

Tx prefix hash: e0700e083530d1790e3d4af5bb517c8ac0c315ceb6008fe69e649b802ecefa9b
Tx public key: d689aa89165ae199acf41d91a473f8f1ef35c828a49deeafaea3e83fa748bffa
Timestamp: 1729156121 Timestamp [UCT]: 2024-10-17 09:08:41 Age [y:d:h:m:s]: 00:001:05:20:24
Block: 1133467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 875 RingCT/type: yes/0
Extra: 01d689aa89165ae199acf41d91a473f8f1ef35c828a49deeafaea3e83fa748bffa02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 681a1da9ed3b6f1c8c2d259b04db9447e424ac89cc3684297d388ccbc1655152 0.600000000000 1616588 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": 1133477, "vin": [ { "gen": { "height": 1133467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "681a1da9ed3b6f1c8c2d259b04db9447e424ac89cc3684297d388ccbc1655152" } } ], "extra": [ 1, 214, 137, 170, 137, 22, 90, 225, 153, 172, 244, 29, 145, 164, 115, 248, 241, 239, 53, 200, 40, 164, 157, 238, 175, 174, 163, 232, 63, 167, 72, 191, 250, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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