Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6cd7e5f541b32c2bcfe7d95a5966e2116c3791650808ef817e69016042cfef6

Tx prefix hash: ab38c5df3b27363e786b873bfd0ff08c56940491f91c28dd72d370e4c14df7d6
Tx public key: 5abd3d111be82e35452477fb0cfad24efb24af97d8e61e5d56253ba841de7c0d
Timestamp: 1709041900 Timestamp [UCT]: 2024-02-27 13:51:40 Age [y:d:h:m:s]: 01:016:15:36:25
Block: 966712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272910 RingCT/type: yes/0
Extra: 015abd3d111be82e35452477fb0cfad24efb24af97d8e61e5d56253ba841de7c0d0211000000020546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f60b4df41b37b4cb419c9dcb19a81a8b97698b7a13185676b8498cf1e557a2ff 0.600000000000 1426483 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": 966722, "vin": [ { "gen": { "height": 966712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f60b4df41b37b4cb419c9dcb19a81a8b97698b7a13185676b8498cf1e557a2ff" } } ], "extra": [ 1, 90, 189, 61, 17, 27, 232, 46, 53, 69, 36, 119, 251, 12, 250, 210, 78, 251, 36, 175, 151, 216, 230, 30, 93, 86, 37, 59, 168, 65, 222, 124, 13, 2, 17, 0, 0, 0, 2, 5, 70, 215, 208, 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