Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45d83b47435e5bb0be1b1783c5a2f83dc6980f389a39b39bedf50cf051ff70bb

Tx prefix hash: 69f901926cacab0e7c7965bdbabd041a192e740abb47e76ae7ce0b403e715993
Tx public key: c5286577279a58691eb2f7f20a0f0a6cf8eae8afb11ab49bde663d5e2678cca7
Timestamp: 1721675037 Timestamp [UCT]: 2024-07-22 19:03:57 Age [y:d:h:m:s]: 00:239:16:35:40
Block: 1071423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171253 RingCT/type: yes/0
Extra: 01c5286577279a58691eb2f7f20a0f0a6cf8eae8afb11ab49bde663d5e2678cca702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b063747a6d870306ee3331866ccfbe12b6021b57eb23896a919b5ce541d98b2 0.600000000000 1543652 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": 1071433, "vin": [ { "gen": { "height": 1071423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b063747a6d870306ee3331866ccfbe12b6021b57eb23896a919b5ce541d98b2" } } ], "extra": [ 1, 197, 40, 101, 119, 39, 154, 88, 105, 30, 178, 247, 242, 10, 15, 10, 108, 248, 234, 232, 175, 177, 26, 180, 155, 222, 102, 61, 94, 38, 120, 204, 167, 2, 17, 0, 0, 0, 3, 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