Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ad4bf8a8f498ae811923035b7b90375ce0f0c2a308060120125d6e4787859c

Tx prefix hash: 426f990b0aeb08f1fd2a217bcc2634fd09da70cb5e3b9aad5c918ab1ebe202b1
Tx public key: 994b4c7cca1b5e2a5664683fc2bb81721662928f8b2795a9a82a2067bf55bc1e
Timestamp: 1723314120 Timestamp [UCT]: 2024-08-10 18:22:00 Age [y:d:h:m:s]: 01:087:07:28:53
Block: 1085027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320854 RingCT/type: yes/0
Extra: 01994b4c7cca1b5e2a5664683fc2bb81721662928f8b2795a9a82a2067bf55bc1e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1e829638ea2622f3724cf49d870cd94629a8a45741a619853ed8b366d38c954 0.600000000000 1559512 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": 1085037, "vin": [ { "gen": { "height": 1085027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1e829638ea2622f3724cf49d870cd94629a8a45741a619853ed8b366d38c954" } } ], "extra": [ 1, 153, 75, 76, 124, 202, 27, 94, 42, 86, 100, 104, 63, 194, 187, 129, 114, 22, 98, 146, 143, 139, 39, 149, 169, 168, 42, 32, 103, 191, 85, 188, 30, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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