Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23db1f0bb3ddee4340a48dc41c64a91a1eba0731abcc1b9dcc19225260b3d93d

Tx prefix hash: 64d59810c069c3cda5bfc1a1f4a7330c7924c83bfcaed4d948eb932abc0ff2e8
Tx public key: 450390c6e2b0ca6560511ef120fe84e15a01c9cb740b221747596174758e0140
Timestamp: 1699866178 Timestamp [UCT]: 2023-11-13 09:02:58 Age [y:d:h:m:s]: 01:151:12:09:09
Block: 890642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369456 RingCT/type: yes/0
Extra: 01450390c6e2b0ca6560511ef120fe84e15a01c9cb740b221747596174758e014002110000001275e3f0e9000000000000000000

1 output(s) for total of 0.686962971000 dcy

stealth address amount amount idx
00: 3602ff681b90e1c59d6f25469672cf4f8a492d89574c5e196cb376ba18467f09 0.686962971000 1346667 of 0

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": 890652, "vin": [ { "gen": { "height": 890642 } } ], "vout": [ { "amount": 686962971, "target": { "key": "3602ff681b90e1c59d6f25469672cf4f8a492d89574c5e196cb376ba18467f09" } } ], "extra": [ 1, 69, 3, 144, 198, 226, 176, 202, 101, 96, 81, 30, 241, 32, 254, 132, 225, 90, 1, 201, 203, 116, 11, 34, 23, 71, 89, 97, 116, 117, 142, 1, 64, 2, 17, 0, 0, 0, 18, 117, 227, 240, 233, 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