Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 599e27990e46e8374ee6e2e9ce66ad2895a9c7265572752f6e70bcde0ae4ad83

Tx prefix hash: aed53cf0084be268fa537f1fd91533b5ed8b0f043cc02e799cd85e21d80d6c22
Tx public key: 99883e197b01679ad77c06281de0357dfb77f8238bcbf50ba89ef4f9e9cba9b5
Timestamp: 1734993834 Timestamp [UCT]: 2024-12-23 22:43:54 Age [y:d:h:m:s]: 00:101:02:56:52
Block: 1181758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72035 RingCT/type: yes/0
Extra: 0199883e197b01679ad77c06281de0357dfb77f8238bcbf50ba89ef4f9e9cba9b50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f344b9d35a3b1095230af5e66ec6c34e72dfb7c2b89333f63c7754cb52c4ca6 0.600000000000 1668183 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": 1181768, "vin": [ { "gen": { "height": 1181758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f344b9d35a3b1095230af5e66ec6c34e72dfb7c2b89333f63c7754cb52c4ca6" } } ], "extra": [ 1, 153, 136, 62, 25, 123, 1, 103, 154, 215, 124, 6, 40, 29, 224, 53, 125, 251, 119, 248, 35, 139, 203, 245, 11, 168, 158, 244, 249, 233, 203, 169, 181, 2, 17, 0, 0, 0, 6, 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