Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72018ccfa426fbd2ced4a519a805519634e5ef85d4a977414312e84484895c63

Tx prefix hash: 50bfc73cd8ee0c0709be96a3318acb3fa067b2ac16c7d7a6c0ba26c3961a0442
Tx public key: f09f6b1e09ea1e2d736b6bc3277ab0c3fe21b78e5cb676097f2283a9841a145f
Timestamp: 1711353914 Timestamp [UCT]: 2024-03-25 08:05:14 Age [y:d:h:m:s]: 01:068:04:53:14
Block: 985900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309741 RingCT/type: yes/0
Extra: 01f09f6b1e09ea1e2d736b6bc3277ab0c3fe21b78e5cb676097f2283a9841a145f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64005ee0e942e68f6ea65dc70fe813215671bd81510ffc760cc94c0593f5ece0 0.600000000000 1446121 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": 985910, "vin": [ { "gen": { "height": 985900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64005ee0e942e68f6ea65dc70fe813215671bd81510ffc760cc94c0593f5ece0" } } ], "extra": [ 1, 240, 159, 107, 30, 9, 234, 30, 45, 115, 107, 107, 195, 39, 122, 176, 195, 254, 33, 183, 142, 92, 182, 118, 9, 127, 34, 131, 169, 132, 26, 20, 95, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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