Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96463642b790e4290527f3c0d94a56fadb65f9543ca128b6b64559c2b000c4b

Tx prefix hash: bfc0f543040d5a95f4af4ab0bf4518dd47f9521c62316cd8adf9269de1350ed7
Tx public key: 4c6731b6a67ef73b5306d5d71b31ce39c6dcf228a469a85c810c6cf4e74c18b1
Timestamp: 1702247092 Timestamp [UCT]: 2023-12-10 22:24:52 Age [y:d:h:m:s]: 01:120:13:34:41
Block: 910377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347312 RingCT/type: yes/0
Extra: 014c6731b6a67ef73b5306d5d71b31ce39c6dcf228a469a85c810c6cf4e74c18b102110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de8cefb1ad74206073691d3fa73ab98d4658ee71739a857dac0f7060c4abd403 0.600000000000 1367528 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": 910387, "vin": [ { "gen": { "height": 910377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de8cefb1ad74206073691d3fa73ab98d4658ee71739a857dac0f7060c4abd403" } } ], "extra": [ 1, 76, 103, 49, 182, 166, 126, 247, 59, 83, 6, 213, 215, 27, 49, 206, 57, 198, 220, 242, 40, 164, 105, 168, 92, 129, 12, 108, 244, 231, 76, 24, 177, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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