Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e90f21beb7933d8bcde7f7235540345fe83a67d7c1ac6055f1448365a467437

Tx prefix hash: 06c8a79699f8ca85c74943b56bd9b44efde24683b6e3aeea11eb57444de93e68
Tx public key: a1d06e9fe1c0d31c06b94f8728599330c6ca1f877fd339dd9564e93d9b46f57a
Timestamp: 1718924043 Timestamp [UCT]: 2024-06-20 22:54:03 Age [y:d:h:m:s]: 00:280:06:05:17
Block: 1048630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200262 RingCT/type: yes/0
Extra: 01a1d06e9fe1c0d31c06b94f8728599330c6ca1f877fd339dd9564e93d9b46f57a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9f7847d294f9aec19b374ef717e92813e2a615e14d5ef039ab5748fbf01abf 0.600000000000 1518715 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": 1048640, "vin": [ { "gen": { "height": 1048630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9f7847d294f9aec19b374ef717e92813e2a615e14d5ef039ab5748fbf01abf" } } ], "extra": [ 1, 161, 208, 110, 159, 225, 192, 211, 28, 6, 185, 79, 135, 40, 89, 147, 48, 198, 202, 31, 135, 127, 211, 57, 221, 149, 100, 233, 61, 155, 70, 245, 122, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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