Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b456e0eb7bdcf5a3189ef01d9aa5f89b935cdd33fffe2086052bc2cf1eb9a84e

Tx prefix hash: 87a9dcb95b9baf3de838cf9923094790fb768148c845cd2ff573723736092249
Tx public key: 3cefab3b172c4b1dd14054aa4e7e512b84da9e5a415238be4ebab3f71dc196d6
Timestamp: 1727300160 Timestamp [UCT]: 2024-09-25 21:36:00 Age [y:d:h:m:s]: 00:149:09:40:16
Block: 1118077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106543 RingCT/type: yes/0
Extra: 013cefab3b172c4b1dd14054aa4e7e512b84da9e5a415238be4ebab3f71dc196d6021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 761345e0b996956436a68fc88fd7bd96748c4e03495105fc044c661a2b62528e 0.600000000000 1599144 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": 1118087, "vin": [ { "gen": { "height": 1118077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "761345e0b996956436a68fc88fd7bd96748c4e03495105fc044c661a2b62528e" } } ], "extra": [ 1, 60, 239, 171, 59, 23, 44, 75, 29, 209, 64, 84, 170, 78, 126, 81, 43, 132, 218, 158, 90, 65, 82, 56, 190, 78, 186, 179, 247, 29, 193, 150, 214, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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