Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cee8f96b4f0d33ff521ba3c9fd51b7ba1aa730b1c9787bb933a207452f8614b7

Tx prefix hash: dd304699685af4f62caadee3dd949c0b191e02265eb4849ff4445b12fd804ef3
Tx public key: e1715aee9feb242e97f38689ff294e13bc2e4367fa42dcdb3ed5113f51d8fc00
Timestamp: 1728522512 Timestamp [UCT]: 2024-10-10 01:08:32 Age [y:d:h:m:s]: 00:254:06:22:48
Block: 1128208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181395 RingCT/type: yes/0
Extra: 01e1715aee9feb242e97f38689ff294e13bc2e4367fa42dcdb3ed5113f51d8fc0002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a6a3e58ce355dfdb372a6efc0b2e14b565b24d6f9c165c66ea8071f81878431 0.600000000000 1611025 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": 1128218, "vin": [ { "gen": { "height": 1128208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a6a3e58ce355dfdb372a6efc0b2e14b565b24d6f9c165c66ea8071f81878431" } } ], "extra": [ 1, 225, 113, 90, 238, 159, 235, 36, 46, 151, 243, 134, 137, 255, 41, 78, 19, 188, 46, 67, 103, 250, 66, 220, 219, 62, 213, 17, 63, 81, 216, 252, 0, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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