Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b19120eaf022c07a0e84a3f8cbc3971ab50bfe10a58a96c9d79f3c17a14e90

Tx prefix hash: 7f036d4022fd52ba135a407597a4e105e5877818daddf5d4f9ca7dd8d2fbc21c
Tx public key: 4956443c8e691fceb081ae9ab6f44000ddd32df0fb5fdf27a00cb9e2876786a8
Timestamp: 1732086324 Timestamp [UCT]: 2024-11-20 07:05:24 Age [y:d:h:m:s]: 00:136:01:36:58
Block: 1157654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97084 RingCT/type: yes/0
Extra: 014956443c8e691fceb081ae9ab6f44000ddd32df0fb5fdf27a00cb9e2876786a80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2edc66f0ee627b8cc40feb73eb0afd3bb405a81b5264453de1569f4212a9bcc3 0.600000000000 1643277 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": 1157664, "vin": [ { "gen": { "height": 1157654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2edc66f0ee627b8cc40feb73eb0afd3bb405a81b5264453de1569f4212a9bcc3" } } ], "extra": [ 1, 73, 86, 68, 60, 142, 105, 31, 206, 176, 129, 174, 154, 182, 244, 64, 0, 221, 211, 45, 240, 251, 95, 223, 39, 160, 12, 185, 226, 135, 103, 134, 168, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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