Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f7fd536aab7cfdcb7cc42ecbb8ecc984b8c8cd78ac59a2ed5e764a692e40f1d

Tx prefix hash: 0f17453fb28d3e628f87f38827042109db883e8fcdd1a31a43bb87d160409036
Tx public key: fd8638c163259bc100b738c0f7b994d807dd3051d0e45cb526d9c0de304290de
Timestamp: 1734829938 Timestamp [UCT]: 2024-12-22 01:12:18 Age [y:d:h:m:s]: 00:000:11:41:37
Block: 1180413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344 RingCT/type: yes/0
Extra: 01fd8638c163259bc100b738c0f7b994d807dd3051d0e45cb526d9c0de304290de0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a165716339998411bdc525ce18f8e506f704f43aee87056eb6bbd962c8b3381 0.600000000000 1666824 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": 1180423, "vin": [ { "gen": { "height": 1180413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a165716339998411bdc525ce18f8e506f704f43aee87056eb6bbd962c8b3381" } } ], "extra": [ 1, 253, 134, 56, 193, 99, 37, 155, 193, 0, 183, 56, 192, 247, 185, 148, 216, 7, 221, 48, 81, 208, 228, 92, 181, 38, 217, 192, 222, 48, 66, 144, 222, 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