Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20afc1c722263147eb0b76d18328ceb774bee85a9306dd1640ef9c220948b4c7

Tx prefix hash: 5a950bf31fe860a21145d8c0f128a646f0016745424f841640ed0fad1d5334a8
Tx public key: 45e1e02432e3cbf4a4ea397dd52277e5ef49041b0cb38a4d4b743d2bb1605755
Timestamp: 1734749808 Timestamp [UCT]: 2024-12-21 02:56:48 Age [y:d:h:m:s]: 00:103:17:32:46
Block: 1179745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73895 RingCT/type: yes/0
Extra: 0145e1e02432e3cbf4a4ea397dd52277e5ef49041b0cb38a4d4b743d2bb16057550211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb0c8f4ad9fdc81ab51230dbe5e947208939ed3120eec39cd918b94979edd41d 0.600000000000 1666144 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": 1179755, "vin": [ { "gen": { "height": 1179745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb0c8f4ad9fdc81ab51230dbe5e947208939ed3120eec39cd918b94979edd41d" } } ], "extra": [ 1, 69, 225, 224, 36, 50, 227, 203, 244, 164, 234, 57, 125, 213, 34, 119, 229, 239, 73, 4, 27, 12, 179, 138, 77, 75, 116, 61, 43, 177, 96, 87, 85, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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