Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e18cae7b520dc8eee3263c97aa033ec8dde74393cf3333a3cadc6c16fbcef546

Tx prefix hash: f506be6f8784af2c085a8fe003cc80c737ec300f607185d05f78a6879d8e2f90
Tx public key: dd2d96b3899fe8cbd563727c6e4e615f42af7edbb829d206d4c3a93b396228dc
Timestamp: 1734935625 Timestamp [UCT]: 2024-12-23 06:33:45 Age [y:d:h:m:s]: 00:176:18:37:58
Block: 1181291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126025 RingCT/type: yes/0
Extra: 01dd2d96b3899fe8cbd563727c6e4e615f42af7edbb829d206d4c3a93b396228dc021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92ae6875e2e6a48d738a5cefe14fd66cf2b7115f1303cef4280bd80639572963 0.600000000000 1667708 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": 1181301, "vin": [ { "gen": { "height": 1181291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92ae6875e2e6a48d738a5cefe14fd66cf2b7115f1303cef4280bd80639572963" } } ], "extra": [ 1, 221, 45, 150, 179, 137, 159, 232, 203, 213, 99, 114, 124, 110, 78, 97, 95, 66, 175, 126, 219, 184, 41, 210, 6, 212, 195, 169, 59, 57, 98, 40, 220, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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