Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9be2842abf46f5d1d39c3b510fb078ae0c6accd9feb67c9f59f15460cf03ec69

Tx prefix hash: f05c0fc4eb15530b0e942a72ae4b24db608ea16a5db6e55e25e2626b88c656b4
Tx public key: 28d5fc0ce05195d0d0acf912d795084068076918013fb85dd370764cf6395e53
Timestamp: 1582254838 Timestamp [UCT]: 2020-02-21 03:13:58 Age [y:d:h:m:s]: 05:254:11:55:41
Block: 69287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1332716 RingCT/type: yes/0
Extra: 0128d5fc0ce05195d0d0acf912d795084068076918013fb85dd370764cf6395e530211000000020aca7173000000000000000000

1 output(s) for total of 361.787233997000 dcy

stealth address amount amount idx
00: ff50c1c4d7f4a0604d9a37032f727d903440218eedab15e802d058661ae5beea 361.787233997000 127743 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": 69297, "vin": [ { "gen": { "height": 69287 } } ], "vout": [ { "amount": 361787233997, "target": { "key": "ff50c1c4d7f4a0604d9a37032f727d903440218eedab15e802d058661ae5beea" } } ], "extra": [ 1, 40, 213, 252, 12, 224, 81, 149, 208, 208, 172, 249, 18, 215, 149, 8, 64, 104, 7, 105, 24, 1, 63, 184, 93, 211, 112, 118, 76, 246, 57, 94, 83, 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