Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d419a516fa07820b1d8bc3b176908a94dc54e9020d197693986d511628b4142

Tx prefix hash: d4c9d2842724cee64ff410c39e5931a82155db93f8718722d7e923b8ff2f635f
Tx public key: 13a0d8063cd5e6953d7acc74c1a1b00aba228c134f4947939fba9a1345e0db95
Timestamp: 1735796480 Timestamp [UCT]: 2025-01-02 05:41:20 Age [y:d:h:m:s]: 00:164:02:21:34
Block: 1188381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117029 RingCT/type: yes/0
Extra: 0113a0d8063cd5e6953d7acc74c1a1b00aba228c134f4947939fba9a1345e0db95021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b681995d9dd9508338c7b176e5a57f84c2e4f9dae52e35d76980b1c3dfc919df 0.600000000000 1674882 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": 1188391, "vin": [ { "gen": { "height": 1188381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b681995d9dd9508338c7b176e5a57f84c2e4f9dae52e35d76980b1c3dfc919df" } } ], "extra": [ 1, 19, 160, 216, 6, 60, 213, 230, 149, 61, 122, 204, 116, 193, 161, 176, 10, 186, 34, 140, 19, 79, 73, 71, 147, 159, 186, 154, 19, 69, 224, 219, 149, 2, 17, 0, 0, 0, 3, 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