Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32e0e7194ed24bde176c96c20c588b3a4955b80404672091c1c49fbb9564a61c

Tx prefix hash: 0a3ed3fb0fcde4c282d0b20cb9fc93293711e60471aa00c55a9077215e72d88a
Tx public key: 82027b694b4e6e882d28f77d31944bffef671720fadfac2c0c9d214e34b9430b
Timestamp: 1703516082 Timestamp [UCT]: 2023-12-25 14:54:42 Age [y:d:h:m:s]: 01:015:13:39:48
Block: 920899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272457 RingCT/type: yes/0
Extra: 0182027b694b4e6e882d28f77d31944bffef671720fadfac2c0c9d214e34b9430b02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5076bf041d85624b65c22b428071aac64b187e3b78f50dc5848188564cb78bba 0.600000000000 1378583 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": 920909, "vin": [ { "gen": { "height": 920899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5076bf041d85624b65c22b428071aac64b187e3b78f50dc5848188564cb78bba" } } ], "extra": [ 1, 130, 2, 123, 105, 75, 78, 110, 136, 45, 40, 247, 125, 49, 148, 75, 255, 239, 103, 23, 32, 250, 223, 172, 44, 12, 157, 33, 78, 52, 185, 67, 11, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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