Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d27d48478d6c4eb50646a63b32a1f352d27427f7b3c62a0411fd0cd5eaaeb5d

Tx prefix hash: fa904a0187224c8f9c738fa0adb12a27235f3149a96e60fa85c5ad93a5c0b9ac
Tx public key: 2114d5a4134a77e1c0de591ae793a7799e4188bb8b729cb834f588e37fc5249c
Timestamp: 1685810377 Timestamp [UCT]: 2023-06-03 16:39:37 Age [y:d:h:m:s]: 01:347:18:23:12
Block: 774349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509769 RingCT/type: yes/0
Extra: 012114d5a4134a77e1c0de591ae793a7799e4188bb8b729cb834f588e37fc5249c02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.668247501000 dcy

stealth address amount amount idx
00: 8157d090e0babe0e6228aa48dea54b9899d874668edebff6800dc09a1c7e30cf 1.668247501000 1223822 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": 774359, "vin": [ { "gen": { "height": 774349 } } ], "vout": [ { "amount": 1668247501, "target": { "key": "8157d090e0babe0e6228aa48dea54b9899d874668edebff6800dc09a1c7e30cf" } } ], "extra": [ 1, 33, 20, 213, 164, 19, 74, 119, 225, 192, 222, 89, 26, 231, 147, 167, 121, 158, 65, 136, 187, 139, 114, 156, 184, 52, 245, 136, 227, 127, 197, 36, 156, 2, 17, 0, 0, 0, 2, 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