Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da1ca1b1c61fac094872f0887454a868a775db5c0cf336df56a24c5cdacd7e4e

Tx prefix hash: f078c02e0ab85555e81e8edbcc448fb8508c82deb2aa41e306c54cf238a721b1
Tx public key: fc6c46de1f828a5c354bcc9c9efcfa74aa86ffd45b0b200ce65dc1713993e4d3
Timestamp: 1725631487 Timestamp [UCT]: 2024-09-06 14:04:47 Age [y:d:h:m:s]: 01:057:22:08:47
Block: 1104251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299799 RingCT/type: yes/0
Extra: 01fc6c46de1f828a5c354bcc9c9efcfa74aa86ffd45b0b200ce65dc1713993e4d3021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c332524d8c588b4d031dfdc31a885c5d4527ba7d88c5c9fdcb8fbd5e50467665 0.600000000000 1581330 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": 1104261, "vin": [ { "gen": { "height": 1104251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c332524d8c588b4d031dfdc31a885c5d4527ba7d88c5c9fdcb8fbd5e50467665" } } ], "extra": [ 1, 252, 108, 70, 222, 31, 130, 138, 92, 53, 75, 204, 156, 158, 252, 250, 116, 170, 134, 255, 212, 91, 11, 32, 12, 230, 93, 193, 113, 57, 147, 228, 211, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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