Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62edd167b15b967d1ce9c7033663eb7c8f19b21a1afa988ccd8a2877a4e56118

Tx prefix hash: 68a8b63b119eeb765fdfcd6666d73a8c80520c4c0ed7576e3f901834f9e21777
Tx public key: eb5e01bac93c96d659d8701854d53160fa2d5652367cb0dbb626e35af401a2ad
Timestamp: 1681139416 Timestamp [UCT]: 2023-04-10 15:10:16 Age [y:d:h:m:s]: 01:319:10:55:33
Block: 735622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489567 RingCT/type: yes/0
Extra: 01eb5e01bac93c96d659d8701854d53160fa2d5652367cb0dbb626e35af401a2ad021100000004b3164c24000000000000000000

1 output(s) for total of 2.241708647000 dcy

stealth address amount amount idx
00: b10871eec9e45918b04eaa280091669e07e3e2a6ed3ae8b2d3ff8f4a432db6a8 2.241708647000 1181969 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": 735632, "vin": [ { "gen": { "height": 735622 } } ], "vout": [ { "amount": 2241708647, "target": { "key": "b10871eec9e45918b04eaa280091669e07e3e2a6ed3ae8b2d3ff8f4a432db6a8" } } ], "extra": [ 1, 235, 94, 1, 186, 201, 60, 150, 214, 89, 216, 112, 24, 84, 213, 49, 96, 250, 45, 86, 82, 54, 124, 176, 219, 182, 38, 227, 90, 244, 1, 162, 173, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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