Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b10a725e4f29de213debeacedda23d624cdaf1919b2e97cd97339356fe86da5e

Tx prefix hash: 419d6b1ffbe5c421672a5ea08187aa00052ffb8cfa7925910c446bd0b01308a5
Tx public key: 81a3b978f54e7e0d25a0be90d96c2f2abccb573d1ef7578cf098aa3c886936d5
Timestamp: 1731465951 Timestamp [UCT]: 2024-11-13 02:45:51 Age [y:d:h:m:s]: 00:166:22:35:13
Block: 1152509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119174 RingCT/type: yes/0
Extra: 0181a3b978f54e7e0d25a0be90d96c2f2abccb573d1ef7578cf098aa3c886936d50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f4f9a5fc7aa9a7b5bc68f71f5d5e0a3f717516a7cfb77491a16ae0d1af1ab53 0.600000000000 1638108 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": 1152519, "vin": [ { "gen": { "height": 1152509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f4f9a5fc7aa9a7b5bc68f71f5d5e0a3f717516a7cfb77491a16ae0d1af1ab53" } } ], "extra": [ 1, 129, 163, 185, 120, 245, 78, 126, 13, 37, 160, 190, 144, 217, 108, 47, 42, 188, 203, 87, 61, 30, 247, 87, 140, 240, 152, 170, 60, 136, 105, 54, 213, 2, 17, 0, 0, 0, 2, 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