Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed575f4c84b74e69b004cd0372a716c04aeffe30592a8ccf44d26138d450043

Tx prefix hash: dea78a54e4beb238eb2bfe32083c3c1f10b0dd7c96a520778754fa0a57323c76
Tx public key: 24251cad7142ef773402d0160293d1334583f3e04dce1d0ae4ce42eae8c3b84a
Timestamp: 1717718326 Timestamp [UCT]: 2024-06-06 23:58:46 Age [y:d:h:m:s]: 01:158:09:13:28
Block: 1038642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371766 RingCT/type: yes/0
Extra: 0124251cad7142ef773402d0160293d1334583f3e04dce1d0ae4ce42eae8c3b84a02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdf3e6a9c9a20d499859aef449bbc6aa16254d246e39af89e895403ec4df2176 0.600000000000 1507203 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": 1038652, "vin": [ { "gen": { "height": 1038642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdf3e6a9c9a20d499859aef449bbc6aa16254d246e39af89e895403ec4df2176" } } ], "extra": [ 1, 36, 37, 28, 173, 113, 66, 239, 119, 52, 2, 208, 22, 2, 147, 209, 51, 69, 131, 243, 224, 77, 206, 29, 10, 228, 206, 66, 234, 232, 195, 184, 74, 2, 17, 0, 0, 0, 11, 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