Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6783c3762d21d4f767e39b4758f0f2f39f854f105222e7506dd7483c5d71d5fc

Tx prefix hash: e29916977fdf352d56034e3b52f44c640af7d6d94a2514d6c4e3af37f57171f9
Tx public key: 1f8eea02c9f7cf7c17990d1f9e880ca35c0263456df85060e1c16e0a3b4e5533
Timestamp: 1698024402 Timestamp [UCT]: 2023-10-23 01:26:42 Age [y:d:h:m:s]: 01:190:21:05:20
Block: 875567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397452 RingCT/type: yes/0
Extra: 011f8eea02c9f7cf7c17990d1f9e880ca35c0263456df85060e1c16e0a3b4e55330211000000014b8f5122000000000000000000

1 output(s) for total of 0.770695961000 dcy

stealth address amount amount idx
00: 087bffaaf789c03dc2d116aada0f20eef89cfb5ba270fd2a3679d0a76721c2f8 0.770695961000 1330829 of 0

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": 875577, "vin": [ { "gen": { "height": 875567 } } ], "vout": [ { "amount": 770695961, "target": { "key": "087bffaaf789c03dc2d116aada0f20eef89cfb5ba270fd2a3679d0a76721c2f8" } } ], "extra": [ 1, 31, 142, 234, 2, 201, 247, 207, 124, 23, 153, 13, 31, 158, 136, 12, 163, 92, 2, 99, 69, 109, 248, 80, 96, 225, 193, 110, 10, 59, 78, 85, 51, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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