Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96525c399c9dde4f534fdf4db04f40e672f1d31c810f2861d26437dbe586089c

Tx prefix hash: 2b9a33bbffc3dd4968cc63bfd285770a42ebfb80c6ca0613f17ec0cb183e7f47
Tx public key: e769210757e2814fb83a1caadb3a2ab3435c172a77bf5ccd2091fe24b5056246
Timestamp: 1712270482 Timestamp [UCT]: 2024-04-04 22:41:22 Age [y:d:h:m:s]: 01:022:06:52:39
Block: 993455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276912 RingCT/type: yes/0
Extra: 01e769210757e2814fb83a1caadb3a2ab3435c172a77bf5ccd2091fe24b50562460211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 309cad9c187274a15a1f8d536aa84016dde6e965b8283a2428cdb24ed3a2eee4 0.600000000000 1453841 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": 993465, "vin": [ { "gen": { "height": 993455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "309cad9c187274a15a1f8d536aa84016dde6e965b8283a2428cdb24ed3a2eee4" } } ], "extra": [ 1, 231, 105, 33, 7, 87, 226, 129, 79, 184, 58, 28, 170, 219, 58, 42, 179, 67, 92, 23, 42, 119, 191, 92, 205, 32, 145, 254, 36, 181, 5, 98, 70, 2, 17, 0, 0, 0, 4, 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