Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5d36958c63f44994a9913174fc82431cb49f449abedb024a95e50f9649d74b4

Tx prefix hash: f12207c202794e8fffef185e8c8a1cae77170a461d3b757931e355900c656c58
Tx public key: 2d81d1f9e70f0148bd47b476285af30c06f67dad53212bd1bcc4ac36bce0dc60
Timestamp: 1702835218 Timestamp [UCT]: 2023-12-17 17:46:58 Age [y:d:h:m:s]: 01:176:11:47:54
Block: 915250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387297 RingCT/type: yes/0
Extra: 012d81d1f9e70f0148bd47b476285af30c06f67dad53212bd1bcc4ac36bce0dc60021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6e0534e09dc17d682b530ce430cb5d2da562bad1cb04b8b75aa0c91d3c7e75 0.600000000000 1372640 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": 915260, "vin": [ { "gen": { "height": 915250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6e0534e09dc17d682b530ce430cb5d2da562bad1cb04b8b75aa0c91d3c7e75" } } ], "extra": [ 1, 45, 129, 209, 249, 231, 15, 1, 72, 189, 71, 180, 118, 40, 90, 243, 12, 6, 246, 125, 173, 83, 33, 43, 209, 188, 196, 172, 54, 188, 224, 220, 96, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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