Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a157bb1493d717dd6bff169f1834960edb305025e4bf89ab86c78565e5d12ecc

Tx prefix hash: 0482e4b81e41a22e244b3b2031986a8ba293c23b70ebb1082165e63b2e6b028f
Tx public key: a472718fcdb6ff55070321762b25e82dcd4d4aeb5e499f9d1a89f0a4426b889d
Timestamp: 1582097394 Timestamp [UCT]: 2020-02-19 07:29:54 Age [y:d:h:m:s]: 04:311:07:31:20
Block: 67875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115072 RingCT/type: yes/0
Extra: 01a472718fcdb6ff55070321762b25e82dcd4d4aeb5e499f9d1a89f0a4426b889d0211000000020aca7173000000000000000000

1 output(s) for total of 365.681302809000 dcy

stealth address amount amount idx
00: d445b5b0bb8a6b261d415c9e0be2cedf0139107a0657a6df63eba62851797415 365.681302809000 125069 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": 67885, "vin": [ { "gen": { "height": 67875 } } ], "vout": [ { "amount": 365681302809, "target": { "key": "d445b5b0bb8a6b261d415c9e0be2cedf0139107a0657a6df63eba62851797415" } } ], "extra": [ 1, 164, 114, 113, 143, 205, 182, 255, 85, 7, 3, 33, 118, 43, 37, 232, 45, 205, 77, 74, 235, 94, 73, 159, 157, 26, 137, 240, 164, 66, 107, 136, 157, 2, 17, 0, 0, 0, 2, 10, 202, 113, 115, 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