Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e9e2628f8e756c793fd940578b805478d0263e4a4b8c3445b3e7ec6c66846e9

Tx prefix hash: c50da92cf1a9b7e685a9332552cf21dca83d415e7fa83bb4b24e195f856a0bed
Tx public key: 096894ac41af72d963f8b114318537b6c28d470e981230e804e46884e7df414b
Timestamp: 1702260362 Timestamp [UCT]: 2023-12-11 02:06:02 Age [y:d:h:m:s]: 01:334:15:09:35
Block: 910483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498026 RingCT/type: yes/0
Extra: 01096894ac41af72d963f8b114318537b6c28d470e981230e804e46884e7df414b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69153967fde0a2c8ab5fffb05487c3e6dc62efe51133ad2f2cc43aca0328eb01 0.600000000000 1367642 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": 910493, "vin": [ { "gen": { "height": 910483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69153967fde0a2c8ab5fffb05487c3e6dc62efe51133ad2f2cc43aca0328eb01" } } ], "extra": [ 1, 9, 104, 148, 172, 65, 175, 114, 217, 99, 248, 177, 20, 49, 133, 55, 182, 194, 141, 71, 14, 152, 18, 48, 232, 4, 228, 104, 132, 231, 223, 65, 75, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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