Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2600c684390ad7293d7156e15ddcb30453d9ab9edc7d6cb6d27742db5f8e3fa

Tx prefix hash: 4e66882026b91b4e23b67383e564b29d90b730e9ef27c18700933cbe20123d2b
Tx public key: fbc41f29a2439c032dd1c1ed7ab0d06728c66ca7ab9ed93646ae42b4b425cfc8
Timestamp: 1709824165 Timestamp [UCT]: 2024-03-07 15:09:25 Age [y:d:h:m:s]: 01:331:23:38:35
Block: 973203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495916 RingCT/type: yes/0
Extra: 01fbc41f29a2439c032dd1c1ed7ab0d06728c66ca7ab9ed93646ae42b4b425cfc802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aad0af51805a6c0b24a8c606233fd75828732f29d54362929562c78ac3c12569 0.600000000000 1433136 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": 973213, "vin": [ { "gen": { "height": 973203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aad0af51805a6c0b24a8c606233fd75828732f29d54362929562c78ac3c12569" } } ], "extra": [ 1, 251, 196, 31, 41, 162, 67, 156, 3, 45, 209, 193, 237, 122, 176, 208, 103, 40, 198, 108, 167, 171, 158, 217, 54, 70, 174, 66, 180, 180, 37, 207, 200, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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