Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 690d7470881e8685cab29b49d31d8568f46bf9d7705bb0364445c3c0c706fa8d

Tx prefix hash: 8c03c2c284794fc4c6773420b90610d7306342dcaf59719a1fdd4f8abb995019
Tx public key: ffb6e086a879113fc613b27a254ee3c26c9b1732f403663b089a9ebb2de66a63
Timestamp: 1731706773 Timestamp [UCT]: 2024-11-15 21:39:33 Age [y:d:h:m:s]: 01:016:20:57:39
Block: 1154513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270504 RingCT/type: yes/0
Extra: 01ffb6e086a879113fc613b27a254ee3c26c9b1732f403663b089a9ebb2de66a63021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f32d53b2bbd5c7a47d3f0cbd01dac37700ca09f48a985914d5a34debacc893dc 0.600000000000 1640126 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": 1154523, "vin": [ { "gen": { "height": 1154513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f32d53b2bbd5c7a47d3f0cbd01dac37700ca09f48a985914d5a34debacc893dc" } } ], "extra": [ 1, 255, 182, 224, 134, 168, 121, 17, 63, 198, 19, 178, 122, 37, 78, 227, 194, 108, 155, 23, 50, 244, 3, 102, 59, 8, 154, 158, 187, 45, 230, 106, 99, 2, 17, 0, 0, 0, 8, 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