Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78ea8fcd6d24d524a222fffcdb4ad2d96acae4b563fa214f8c14463373ea1d22

Tx prefix hash: c3f1184fdfbb3d56a14637035916b58ea65e823d151262b6a50e6e92572f02e1
Tx public key: b160088e6624fdd9d8e31fddbc1b1ba6bcad2b8bab7a4ea609bd9275dae20595
Timestamp: 1732443123 Timestamp [UCT]: 2024-11-24 10:12:03 Age [y:d:h:m:s]: 00:351:19:15:01
Block: 1160611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248965 RingCT/type: yes/0
Extra: 01b160088e6624fdd9d8e31fddbc1b1ba6bcad2b8bab7a4ea609bd9275dae20595021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90848b14fe5604d291fff8ec28a40a04b381c80d70c9f9be321d0bcfd74eeb02 0.600000000000 1646258 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": 1160621, "vin": [ { "gen": { "height": 1160611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90848b14fe5604d291fff8ec28a40a04b381c80d70c9f9be321d0bcfd74eeb02" } } ], "extra": [ 1, 177, 96, 8, 142, 102, 36, 253, 217, 216, 227, 31, 221, 188, 27, 27, 166, 188, 173, 43, 139, 171, 122, 78, 166, 9, 189, 146, 117, 218, 226, 5, 149, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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