Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84514f567164ee231c0ef451c2256516c149b38996100ec8444ea7aa308090b3

Tx prefix hash: 823325564aedb957b615c853168321ecfd71deef29059c826096ba495d30de3d
Tx public key: 3e06f9c15b0e0a8a15642309b3c526a4a0fb6d3328e7f2774615576b65e492f0
Timestamp: 1720329447 Timestamp [UCT]: 2024-07-07 05:17:27 Age [y:d:h:m:s]: 00:252:13:05:45
Block: 1060284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180438 RingCT/type: yes/0
Extra: 013e06f9c15b0e0a8a15642309b3c526a4a0fb6d3328e7f2774615576b65e492f002110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5214416e9c42aa686537651eb773de6c3065a55a4917a1e289a6db0e84bec52d 0.600000000000 1530755 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": 1060294, "vin": [ { "gen": { "height": 1060284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5214416e9c42aa686537651eb773de6c3065a55a4917a1e289a6db0e84bec52d" } } ], "extra": [ 1, 62, 6, 249, 193, 91, 14, 10, 138, 21, 100, 35, 9, 179, 197, 38, 164, 160, 251, 109, 51, 40, 231, 242, 119, 70, 21, 87, 107, 101, 228, 146, 240, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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