Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d87d15db2f029e85446e387d2e34c200f073d732c40edf1aead41c99859c389

Tx prefix hash: 25dce9169191beb10fa5ad68acb9d44655152c8b21e6b04a6623305f03d316c9
Tx public key: abb5a8a18c68cb2611d35fdb0f6a1f42e7af59db231276fff83b8291145ee71c
Timestamp: 1582516986 Timestamp [UCT]: 2020-02-24 04:03:06 Age [y:d:h:m:s]: 04:280:18:10:52
Block: 71414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093143 RingCT/type: yes/0
Extra: 01abb5a8a18c68cb2611d35fdb0f6a1f42e7af59db231276fff83b8291145ee71c02110000000356c366d3000000000000000000

1 output(s) for total of 355.949868169000 dcy

stealth address amount amount idx
00: 14a66114a5aa9d42117a48386bb7dd6e99b31427d93056f3f2ca7daa0c81c352 355.949868169000 131897 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": 71424, "vin": [ { "gen": { "height": 71414 } } ], "vout": [ { "amount": 355949868169, "target": { "key": "14a66114a5aa9d42117a48386bb7dd6e99b31427d93056f3f2ca7daa0c81c352" } } ], "extra": [ 1, 171, 181, 168, 161, 140, 104, 203, 38, 17, 211, 95, 219, 15, 106, 31, 66, 231, 175, 89, 219, 35, 18, 118, 255, 248, 59, 130, 145, 20, 94, 231, 28, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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