Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ebd3e6a9bccf8c6c744953a3b2f4858a081a74f5afe772d00aa9ff5030b0b0

Tx prefix hash: 420d3bd3b4013835c5197f30afb26575e2d929277ce709229b0752b741a801d3
Tx public key: ef12216aad9c613a8b2791f4c59fe00274dc8e1ee6a895ed8d70c1ec202d3176
Timestamp: 1712583252 Timestamp [UCT]: 2024-04-08 13:34:12 Age [y:d:h:m:s]: 01:237:16:10:31
Block: 996040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428592 RingCT/type: yes/0
Extra: 01ef12216aad9c613a8b2791f4c59fe00274dc8e1ee6a895ed8d70c1ec202d317602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd3ed87803d75982c2bb91041909ef4534c04852ec66af24cd8e9dbe3ce73b28 0.600000000000 1456456 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": 996050, "vin": [ { "gen": { "height": 996040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd3ed87803d75982c2bb91041909ef4534c04852ec66af24cd8e9dbe3ce73b28" } } ], "extra": [ 1, 239, 18, 33, 106, 173, 156, 97, 58, 139, 39, 145, 244, 197, 159, 224, 2, 116, 220, 142, 30, 230, 168, 149, 237, 141, 112, 193, 236, 32, 45, 49, 118, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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