Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4457e982140247736b6b9adaf1b5b3705a0625f2b6f84b48f5e73b3852bb9af

Tx prefix hash: 3697a2a161668f0b5afe807657a642a6a9c9681bc1948585ef96d41b62ebb765
Tx public key: 0b04b05f3e0a74d3e415b3e4d32b9dc12cb2edd0d96a1ac4fc851585e86ad64f
Timestamp: 1711138696 Timestamp [UCT]: 2024-03-22 20:18:16 Age [y:d:h:m:s]: 01:291:07:32:30
Block: 984115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466953 RingCT/type: yes/0
Extra: 010b04b05f3e0a74d3e415b3e4d32b9dc12cb2edd0d96a1ac4fc851585e86ad64f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bef6bc1b0e879b1c2ae247881f570cd8b2faf93180589cf756ee2586c861d8ab 0.600000000000 1444270 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": 984125, "vin": [ { "gen": { "height": 984115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bef6bc1b0e879b1c2ae247881f570cd8b2faf93180589cf756ee2586c861d8ab" } } ], "extra": [ 1, 11, 4, 176, 95, 62, 10, 116, 211, 228, 21, 179, 228, 211, 43, 157, 193, 44, 178, 237, 208, 217, 106, 26, 196, 252, 133, 21, 133, 232, 106, 214, 79, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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