Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ac5230806196d2b0bda562a3635ba8640ff8863f682cdf2419e68ad24841667

Tx prefix hash: c367d18bef32f1db5bd511de32ce85ee4d347b1de875dbf1c9b5a7e25dc572b5
Tx public key: 6b081a539a9c81ddfeaf0d90404a980ef6e3d3c43ec3077f11c5777a4283d7fe
Timestamp: 1706095217 Timestamp [UCT]: 2024-01-24 11:20:17 Age [y:d:h:m:s]: 01:084:22:59:43
Block: 942243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321835 RingCT/type: yes/0
Extra: 016b081a539a9c81ddfeaf0d90404a980ef6e3d3c43ec3077f11c5777a4283d7fe0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11ea7b6249b8097f620e7248708d96c2c431b3109055e31e5c3698da8693fcf6 0.600000000000 1400409 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": 942253, "vin": [ { "gen": { "height": 942243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11ea7b6249b8097f620e7248708d96c2c431b3109055e31e5c3698da8693fcf6" } } ], "extra": [ 1, 107, 8, 26, 83, 154, 156, 129, 221, 254, 175, 13, 144, 64, 74, 152, 14, 246, 227, 211, 196, 62, 195, 7, 127, 17, 197, 119, 122, 66, 131, 215, 254, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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