Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fb99143ad4f34ec6da3e22c5e9c13ca779ef41274aa69ee69ba26aea2ec3cab

Tx prefix hash: 6a69af701099885b42ea59c8115c8580306c5359d87ecc08b2fee87c6620f860
Tx public key: 73821a19af64eae9a4776e2959037320d0a24a3d95eb88c3f50db0d5e0315320
Timestamp: 1728141326 Timestamp [UCT]: 2024-10-05 15:15:26 Age [y:d:h:m:s]: 00:203:03:55:03
Block: 1125049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145021 RingCT/type: yes/0
Extra: 0173821a19af64eae9a4776e2959037320d0a24a3d95eb88c3f50db0d5e0315320021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2a8f0ff1f76c83bf06a4027a6071e66309bee588537d546eb49b30f1cbc2d59 0.600000000000 1607722 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": 1125059, "vin": [ { "gen": { "height": 1125049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2a8f0ff1f76c83bf06a4027a6071e66309bee588537d546eb49b30f1cbc2d59" } } ], "extra": [ 1, 115, 130, 26, 25, 175, 100, 234, 233, 164, 119, 110, 41, 89, 3, 115, 32, 208, 162, 74, 61, 149, 235, 136, 195, 245, 13, 176, 213, 224, 49, 83, 32, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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