Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9772db6988eee0d8445d5bd2770ef5534dfb0235040b7f3c40ad0a52fc9abe64

Tx prefix hash: 35194ececa67171fce9cdeba973221dacc17999fbda960a4361f997fe7e044bb
Tx public key: 4535c35619f545ffead0b0d0e3bead910eb47916ea0d88ed9db4e4eb9b5e8f8f
Timestamp: 1729639911 Timestamp [UCT]: 2024-10-22 23:31:51 Age [y:d:h:m:s]: 00:241:16:17:34
Block: 1137443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172409 RingCT/type: yes/0
Extra: 014535c35619f545ffead0b0d0e3bead910eb47916ea0d88ed9db4e4eb9b5e8f8f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ad1ae061b9e90e4aa36dd837b7074e907ffdf84cca7686b80335fab39ac3592 0.600000000000 1620936 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": 1137453, "vin": [ { "gen": { "height": 1137443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ad1ae061b9e90e4aa36dd837b7074e907ffdf84cca7686b80335fab39ac3592" } } ], "extra": [ 1, 69, 53, 195, 86, 25, 245, 69, 255, 234, 208, 176, 208, 227, 190, 173, 145, 14, 180, 121, 22, 234, 13, 136, 237, 157, 180, 228, 235, 155, 94, 143, 143, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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