Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e46eb90433c47a4cb4014c0434d9f9d7cd5d05e62d20da78ad9113ca1bc65f4e

Tx prefix hash: 8e2915325faeeba11cd296516093427ec8d443f537c124b1ee7af7f9509692f7
Tx public key: a8dbf64127783e7e8dc52390d091fcbf81618f29912d4c8ebd0a74ac2360c272
Timestamp: 1733140637 Timestamp [UCT]: 2024-12-02 11:57:17 Age [y:d:h:m:s]: 00:127:16:25:14
Block: 1166397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91056 RingCT/type: yes/0
Extra: 01a8dbf64127783e7e8dc52390d091fcbf81618f29912d4c8ebd0a74ac2360c272021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50b7bf169c44e22f0ec5a2ae9cbba810e3cb492b519b0928643c16c800f13ee5 0.600000000000 1652084 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": 1166407, "vin": [ { "gen": { "height": 1166397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50b7bf169c44e22f0ec5a2ae9cbba810e3cb492b519b0928643c16c800f13ee5" } } ], "extra": [ 1, 168, 219, 246, 65, 39, 120, 62, 126, 141, 197, 35, 144, 208, 145, 252, 191, 129, 97, 143, 41, 145, 45, 76, 142, 189, 10, 116, 172, 35, 96, 194, 114, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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