Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc394e20599fd06015fc81017f94737e1ac56bbdd104e9d6937ad5ac2714ec91

Tx prefix hash: 891edb5169eea66fd0b0e3459be860c2dcfb0c79499ad9f6fa5e8087f03d4394
Tx public key: b35d4e1372a99108c7da0a93645281d0992e8977c011f8a487f1ba4247b42c99
Timestamp: 1581242522 Timestamp [UCT]: 2020-02-09 10:02:02 Age [y:d:h:m:s]: 04:281:23:49:37
Block: 61189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093700 RingCT/type: yes/0
Extra: 01b35d4e1372a99108c7da0a93645281d0992e8977c011f8a487f1ba4247b42c990211000000074943cd9f000000000000000000

1 output(s) for total of 384.818780373000 dcy

stealth address amount amount idx
00: fdd8eee669b5f2d3d6cb65296bb8a0ff4321005f46337c8937c80844827472a6 384.818780373000 112767 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": 61199, "vin": [ { "gen": { "height": 61189 } } ], "vout": [ { "amount": 384818780373, "target": { "key": "fdd8eee669b5f2d3d6cb65296bb8a0ff4321005f46337c8937c80844827472a6" } } ], "extra": [ 1, 179, 93, 78, 19, 114, 169, 145, 8, 199, 218, 10, 147, 100, 82, 129, 208, 153, 46, 137, 119, 192, 17, 248, 164, 135, 241, 186, 66, 71, 180, 44, 153, 2, 17, 0, 0, 0, 7, 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