Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8762e3737617febedbc0fa5b6e16769181e2fbbe36ee279f2d1b6745e17ff31

Tx prefix hash: 894d7465a1853489ea38d01993f45db870eac522779ae47421d14dd15e8a82cd
Tx public key: 72d22384e857f10586d299d807e5c8274bc6e5deb3b583dc14963d1f0a6bea6c
Timestamp: 1720189248 Timestamp [UCT]: 2024-07-05 14:20:48 Age [y:d:h:m:s]: 00:232:14:32:20
Block: 1059119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166147 RingCT/type: yes/0
Extra: 0172d22384e857f10586d299d807e5c8274bc6e5deb3b583dc14963d1f0a6bea6c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e84bc6c6b1c6a6f9ac758a1d94faba5302a633cec215e96b7dd9139434a3f0b0 0.600000000000 1529580 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": 1059129, "vin": [ { "gen": { "height": 1059119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e84bc6c6b1c6a6f9ac758a1d94faba5302a633cec215e96b7dd9139434a3f0b0" } } ], "extra": [ 1, 114, 210, 35, 132, 232, 87, 241, 5, 134, 210, 153, 216, 7, 229, 200, 39, 75, 198, 229, 222, 179, 181, 131, 220, 20, 150, 61, 31, 10, 107, 234, 108, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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