Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a59eda85fa87374d7015fdc9bd359b7dcc70972a063b14bd5c46f0dcaa110143

Tx prefix hash: f4ab5e4fa8ee1a7937c7540065eb0ba9c42b35c4ce3775ed2b17068d5c63714f
Tx public key: b34b2a817cbe9ac3230ce2d42625a72307825e88a6e574737a60cff1ae5a3344
Timestamp: 1698589823 Timestamp [UCT]: 2023-10-29 14:30:23 Age [y:d:h:m:s]: 01:180:01:15:08
Block: 880265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389697 RingCT/type: yes/0
Extra: 01b34b2a817cbe9ac3230ce2d42625a72307825e88a6e574737a60cff1ae5a334402110000000775e3f0e9000000000000000000

1 output(s) for total of 0.743561084000 dcy

stealth address amount amount idx
00: 47f3bcd83c3af2a179ffe2c1f9115fb576d5c87511d68815e849a2401ed977da 0.743561084000 1335811 of 0

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": 880275, "vin": [ { "gen": { "height": 880265 } } ], "vout": [ { "amount": 743561084, "target": { "key": "47f3bcd83c3af2a179ffe2c1f9115fb576d5c87511d68815e849a2401ed977da" } } ], "extra": [ 1, 179, 75, 42, 129, 124, 190, 154, 195, 35, 12, 226, 212, 38, 37, 167, 35, 7, 130, 94, 136, 166, 229, 116, 115, 122, 96, 207, 241, 174, 90, 51, 68, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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