Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d334e7f2608c5ded756fe8ccf03a5d4204e399131592d9854a213a0be0d87d5

Tx prefix hash: 1dd8e3af240950d90bc3f9b6f9393c9678fe58322698b7208adf39a963e9a6a0
Tx public key: 2ea988a9d9356e2a49de62bfc44f9a1a4498287565efc148e182c51fe8d1b454
Timestamp: 1737365882 Timestamp [UCT]: 2025-01-20 09:38:02 Age [y:d:h:m:s]: 00:149:06:07:18
Block: 1201329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106424 RingCT/type: yes/0
Extra: 012ea988a9d9356e2a49de62bfc44f9a1a4498287565efc148e182c51fe8d1b4540211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26a212c18769f15c2c132c444cd35243b513558648f64bf3f1382e98b1e220e7 0.600000000000 1687978 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": 1201339, "vin": [ { "gen": { "height": 1201329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26a212c18769f15c2c132c444cd35243b513558648f64bf3f1382e98b1e220e7" } } ], "extra": [ 1, 46, 169, 136, 169, 217, 53, 110, 42, 73, 222, 98, 191, 196, 79, 154, 26, 68, 152, 40, 117, 101, 239, 193, 72, 225, 130, 197, 31, 232, 209, 180, 84, 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