Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88af5551f818bbf778f6e7bd0b21c23e0e40af472c33b88f3702bfc08be2ed68

Tx prefix hash: bbc4fd3bd4b2c3849968e34c9425f1799b61f25de1d6cdf0abaf97b68e2ab578
Tx public key: 3c74adcb9534458ec59b6a3e3bb91a5b4680fff18c48b13a78f928e41c291956
Timestamp: 1721752141 Timestamp [UCT]: 2024-07-23 16:29:01 Age [y:d:h:m:s]: 00:152:12:32:12
Block: 1072075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109168 RingCT/type: yes/0
Extra: 013c74adcb9534458ec59b6a3e3bb91a5b4680fff18c48b13a78f928e41c291956021100000015e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f603ac824a689317d5f804e44a911f6910059f251bd7b60812009eb70b5b7649 0.600000000000 1544518 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": 1072085, "vin": [ { "gen": { "height": 1072075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f603ac824a689317d5f804e44a911f6910059f251bd7b60812009eb70b5b7649" } } ], "extra": [ 1, 60, 116, 173, 203, 149, 52, 69, 142, 197, 155, 106, 62, 59, 185, 26, 91, 70, 128, 255, 241, 140, 72, 177, 58, 120, 249, 40, 228, 28, 41, 25, 86, 2, 17, 0, 0, 0, 21, 233, 20, 221, 21, 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