Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fc453d7d7f667ea0c3c10c97ba31e5cbcf481cb66172582c03f6809935bbc2d

Tx prefix hash: 7a8494c6c828f7eee295e72165e34ab52b4fc7d9ea95d510d773c9e4967d8a5e
Tx public key: 3d0482aabdd329673911286c8b35ee854d9f9c150dd9635da86430f6be0001cc
Timestamp: 1582177642 Timestamp [UCT]: 2020-02-20 05:47:22 Age [y:d:h:m:s]: 05:058:23:59:31
Block: 68585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195353 RingCT/type: yes/0
Extra: 013d0482aabdd329673911286c8b35ee854d9f9c150dd9635da86430f6be0001cc0211000000174943cd9f000000000000000000

1 output(s) for total of 363.705802496000 dcy

stealth address amount amount idx
00: 14c53560677c3d2045974caf983a9ac9a33dd1d33580a20e7e15c22ee7f5ac7b 363.705802496000 126434 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": 68595, "vin": [ { "gen": { "height": 68585 } } ], "vout": [ { "amount": 363705802496, "target": { "key": "14c53560677c3d2045974caf983a9ac9a33dd1d33580a20e7e15c22ee7f5ac7b" } } ], "extra": [ 1, 61, 4, 130, 170, 189, 211, 41, 103, 57, 17, 40, 108, 139, 53, 238, 133, 77, 159, 156, 21, 13, 217, 99, 93, 168, 100, 48, 246, 190, 0, 1, 204, 2, 17, 0, 0, 0, 23, 73, 67, 205, 159, 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