Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59cce5e9c129604bfbda1b5046ce90902ac95dc573e12a4cb4c1e2a2b7e50ddd

Tx prefix hash: c955db4ffbe362e0dc292dd26c4b94721c1180babce749dcbfd984df9453e46d
Tx public key: 2d9f0c5011fde1dc1bdad7ff0b4a76871feb1700b8f594c2dcfbc9914a4c6986
Timestamp: 1705801631 Timestamp [UCT]: 2024-01-21 01:47:11 Age [y:d:h:m:s]: 01:080:01:42:57
Block: 939806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318343 RingCT/type: yes/0
Extra: 012d9f0c5011fde1dc1bdad7ff0b4a76871feb1700b8f594c2dcfbc9914a4c69860211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea120e4ce7d905f8dc9959ba1f96a24b9ec8a174d66a948dd317eec8fe8fb5ef 0.600000000000 1397938 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": 939816, "vin": [ { "gen": { "height": 939806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea120e4ce7d905f8dc9959ba1f96a24b9ec8a174d66a948dd317eec8fe8fb5ef" } } ], "extra": [ 1, 45, 159, 12, 80, 17, 253, 225, 220, 27, 218, 215, 255, 11, 74, 118, 135, 31, 235, 23, 0, 184, 245, 148, 194, 220, 251, 201, 145, 74, 76, 105, 134, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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