Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d17e91ce88e7c8901141d1fa9bee6aa1a7e9d543bc60d9fa4f40e5ee3ca5dfe0

Tx prefix hash: 57cbb490408cf7f8ee741e2abdd52424bc94b3e0f961c52acbde901cd9702756
Tx public key: 62d8a8e33be5e758eb1e3490516a027b33e648400382f991ba91bd2cb5362c47
Timestamp: 1732278321 Timestamp [UCT]: 2024-11-22 12:25:21 Age [y:d:h:m:s]: 00:001:17:32:26
Block: 1159250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1240 RingCT/type: yes/0
Extra: 0162d8a8e33be5e758eb1e3490516a027b33e648400382f991ba91bd2cb5362c47021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 280234a0b6c22acf3559995ff91eda7bcedda671da5dfbdf5be699f5ba0e1fc5 0.600000000000 1644883 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": 1159260, "vin": [ { "gen": { "height": 1159250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "280234a0b6c22acf3559995ff91eda7bcedda671da5dfbdf5be699f5ba0e1fc5" } } ], "extra": [ 1, 98, 216, 168, 227, 59, 229, 231, 88, 235, 30, 52, 144, 81, 106, 2, 123, 51, 230, 72, 64, 3, 130, 249, 145, 186, 145, 189, 44, 181, 54, 44, 71, 2, 17, 0, 0, 0, 2, 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