Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57690e2257527e47279cf0bcd1745c40149b88c7eb8c360e37f8c6f0e28dc555

Tx prefix hash: 4ef5e4f65bd9d39195f2824c7b43a19862bd86208df5a5375925f65691f201dc
Tx public key: 0df19714dba4a55da10d31bcaa246e8c5f35fee9544899f2dcbbdbe49ad3f929
Timestamp: 1644627223 Timestamp [UCT]: 2022-02-12 00:53:43 Age [y:d:h:m:s]: 03:262:18:21:30
Block: 436655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 965477 RingCT/type: yes/0
Extra: 010df19714dba4a55da10d31bcaa246e8c5f35fee9544899f2dcbbdbe49ad3f929021100000012bf7ee4e7000000000000000000

1 output(s) for total of 21.937191136000 dcy

stealth address amount amount idx
00: 7818065184635601f808aa9f777e8ba39fc66c91c3f4c686c86542bb32048b8a 21.937191136000 848074 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": 436665, "vin": [ { "gen": { "height": 436655 } } ], "vout": [ { "amount": 21937191136, "target": { "key": "7818065184635601f808aa9f777e8ba39fc66c91c3f4c686c86542bb32048b8a" } } ], "extra": [ 1, 13, 241, 151, 20, 219, 164, 165, 93, 161, 13, 49, 188, 170, 36, 110, 140, 95, 53, 254, 233, 84, 72, 153, 242, 220, 187, 219, 228, 154, 211, 249, 41, 2, 17, 0, 0, 0, 18, 191, 126, 228, 231, 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