Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 096b6d5fd04dfc08da667a4fd74d3e81a3b0e8090e98e550c0f05b2d2e1de092

Tx prefix hash: fbe87e6f036a1907b8d9f36b423e58a44fc23a4f330761000280dfb8f7cc4690
Tx public key: 8f3f34f36941d03a8acd3241cdef6a79b0590cbc07ac59b6f44afd89a5795029
Timestamp: 1584923245 Timestamp [UCT]: 2020-03-23 00:27:25 Age [y:d:h:m:s]: 05:035:21:07:12
Block: 86961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1183177 RingCT/type: yes/0
Extra: 018f3f34f36941d03a8acd3241cdef6a79b0590cbc07ac59b6f44afd89a579502902110000009fc2c2f844000000000000000000

1 output(s) for total of 316.127944510000 dcy

stealth address amount amount idx
00: 53fd08baba82f1d9c126ef9e1dc99e19423ea78e8c77cbff559a4f976f2f9c89 316.127944510000 156825 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": 86971, "vin": [ { "gen": { "height": 86961 } } ], "vout": [ { "amount": 316127944510, "target": { "key": "53fd08baba82f1d9c126ef9e1dc99e19423ea78e8c77cbff559a4f976f2f9c89" } } ], "extra": [ 1, 143, 63, 52, 243, 105, 65, 208, 58, 138, 205, 50, 65, 205, 239, 106, 121, 176, 89, 12, 188, 7, 172, 89, 182, 244, 74, 253, 137, 165, 121, 80, 41, 2, 17, 0, 0, 0, 159, 194, 194, 248, 68, 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