Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ddf8d7bd19d69b2b112526bd6f25dc1e67104c74fdb054ddbde8ca1fccb15f1

Tx prefix hash: 5dbd381dfa0b88241f5e8d7caadace878c23d81d8c6d9c16b9287029cfa893cc
Tx public key: 6d413c0bceeef49c2e7470429b12e8e7f9558316d47f883b22b24d6c79c4c23e
Timestamp: 1732396086 Timestamp [UCT]: 2024-11-23 21:08:06 Age [y:d:h:m:s]: 00:033:17:28:16
Block: 1160225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24134 RingCT/type: yes/0
Extra: 016d413c0bceeef49c2e7470429b12e8e7f9558316d47f883b22b24d6c79c4c23e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1f22e513261cea762847da7a11b1f29886f4c22ada9bac852a7c0ff940fc70b 0.600000000000 1645868 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": 1160235, "vin": [ { "gen": { "height": 1160225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1f22e513261cea762847da7a11b1f29886f4c22ada9bac852a7c0ff940fc70b" } } ], "extra": [ 1, 109, 65, 60, 11, 206, 238, 244, 156, 46, 116, 112, 66, 155, 18, 232, 231, 249, 85, 131, 22, 212, 127, 136, 59, 34, 178, 77, 108, 121, 196, 194, 62, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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