Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af9e809ce16059a4cce2fa736de2b9754425b2040358a6ee0e8898ddb261745a

Tx prefix hash: 3e2801942fe42b3b88103cdde5b0ba4a2497f9683b8a45dce96cc6a50d6a5798
Tx public key: 87de6c1dd63356d2b87db2fb69c13c5c54878a9ab15e7f45a03e04e5af65daad
Timestamp: 1734499567 Timestamp [UCT]: 2024-12-18 05:26:07 Age [y:d:h:m:s]: 00:121:10:07:28
Block: 1177683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86554 RingCT/type: yes/0
Extra: 0187de6c1dd63356d2b87db2fb69c13c5c54878a9ab15e7f45a03e04e5af65daad0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fc306ad1bf94152d8f4c6b45816f3a8c852fcd6793e5f24cccdbff055a29451 0.600000000000 1664056 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": 1177693, "vin": [ { "gen": { "height": 1177683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fc306ad1bf94152d8f4c6b45816f3a8c852fcd6793e5f24cccdbff055a29451" } } ], "extra": [ 1, 135, 222, 108, 29, 214, 51, 86, 210, 184, 125, 178, 251, 105, 193, 60, 92, 84, 135, 138, 154, 177, 94, 127, 69, 160, 62, 4, 229, 175, 101, 218, 173, 2, 17, 0, 0, 0, 1, 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