Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3f376e678c28a19f2fb2a8f56fa68c8916b300f9adc39e75bcc8bd97e4d5fcc

Tx prefix hash: 7fb7df988aa34fe2894e322f444666935bab4a72f727cc79e7414312c81e8ab8
Tx public key: e89a6c8179a1d0c125ab7bacbaa160b6f45e9d6051e6f7f44786abcb9f5c4f4f
Timestamp: 1722396812 Timestamp [UCT]: 2024-07-31 03:33:32 Age [y:d:h:m:s]: 00:116:18:09:07
Block: 1077424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83533 RingCT/type: yes/0
Extra: 01e89a6c8179a1d0c125ab7bacbaa160b6f45e9d6051e6f7f44786abcb9f5c4f4f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af097d89a95d25585399ff91b3b1d5dcf0340b1dc566993d0279aa7117ea22e4 0.600000000000 1549971 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": 1077434, "vin": [ { "gen": { "height": 1077424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af097d89a95d25585399ff91b3b1d5dcf0340b1dc566993d0279aa7117ea22e4" } } ], "extra": [ 1, 232, 154, 108, 129, 121, 161, 208, 193, 37, 171, 123, 172, 186, 161, 96, 182, 244, 94, 157, 96, 81, 230, 247, 244, 71, 134, 171, 203, 159, 92, 79, 79, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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