Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa4cbd9ee8416ec9a35417cd4fb953874279c65d0d1469101658b6d3e25c34fb

Tx prefix hash: f614d7e4155ac02f1df1cd3479ebb63536e0e1be2289d5dbed41a0ec75ec2b48
Tx public key: 03288dadb22c826dca747cb9d3c731fb7b16772179cfe344f15655a2c0c5c992
Timestamp: 1732501806 Timestamp [UCT]: 2024-11-25 02:30:06 Age [y:d:h:m:s]: 00:144:06:39:44
Block: 1161103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102936 RingCT/type: yes/0
Extra: 0103288dadb22c826dca747cb9d3c731fb7b16772179cfe344f15655a2c0c5c9920211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1d9afeb34e4b1561f1ea62725532073cbc06a734e31832e3d12a08235425afc 0.600000000000 1646754 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": 1161113, "vin": [ { "gen": { "height": 1161103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1d9afeb34e4b1561f1ea62725532073cbc06a734e31832e3d12a08235425afc" } } ], "extra": [ 1, 3, 40, 141, 173, 178, 44, 130, 109, 202, 116, 124, 185, 211, 199, 49, 251, 123, 22, 119, 33, 121, 207, 227, 68, 241, 86, 85, 162, 192, 197, 201, 146, 2, 17, 0, 0, 0, 4, 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