Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f6f40b5ef048e918fbcc10b226ff75a79dec2660c810a57179fac36ee52eeb

Tx prefix hash: 5c25af0bd0b6e8409aab40d58c4fe100d68236d7d63794e5768bc14c75a0701d
Tx public key: 581a4b6d4f013cf8b5f0c47f1b397486f1097aac4437afc4522102241fc6b47b
Timestamp: 1722412556 Timestamp [UCT]: 2024-07-31 07:55:56 Age [y:d:h:m:s]: 00:260:13:41:20
Block: 1077552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186131 RingCT/type: yes/0
Extra: 01581a4b6d4f013cf8b5f0c47f1b397486f1097aac4437afc4522102241fc6b47b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66504842b0cdf990739da614cdcb49b0ec49c33b955404b57c5c477db3df8dc8 0.600000000000 1550103 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": 1077562, "vin": [ { "gen": { "height": 1077552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66504842b0cdf990739da614cdcb49b0ec49c33b955404b57c5c477db3df8dc8" } } ], "extra": [ 1, 88, 26, 75, 109, 79, 1, 60, 248, 181, 240, 196, 127, 27, 57, 116, 134, 241, 9, 122, 172, 68, 55, 175, 196, 82, 33, 2, 36, 31, 198, 180, 123, 2, 17, 0, 0, 0, 1, 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