Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a9da0fddeb829b3fe66d7f731ce7410e4afd952aa0b026ed40281912ce0610

Tx prefix hash: a2d9b9303a753ad60e842ff6b1825a1fe5afa5b86b45ff7586b206b71d0465a9
Tx public key: 6c273b3da5eb9f9062ea76d0f2b038278c7f5922e6a67ea4cd2f71f5472d5a2c
Timestamp: 1637351871 Timestamp [UCT]: 2021-11-19 19:57:51 Age [y:d:h:m:s]: 03:046:18:08:24
Block: 377805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 812270 RingCT/type: yes/0
Extra: 016c273b3da5eb9f9062ea76d0f2b038278c7f5922e6a67ea4cd2f71f5472d5a2c02110000000eb494d89c000000000000000000

1 output(s) for total of 34.369687596000 dcy

stealth address amount amount idx
00: 5944afbe755b8672250fcf27793f82469ec21d5b543c83aa2ee681097eeeb80f 34.369687596000 764132 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": 377815, "vin": [ { "gen": { "height": 377805 } } ], "vout": [ { "amount": 34369687596, "target": { "key": "5944afbe755b8672250fcf27793f82469ec21d5b543c83aa2ee681097eeeb80f" } } ], "extra": [ 1, 108, 39, 59, 61, 165, 235, 159, 144, 98, 234, 118, 208, 242, 176, 56, 39, 140, 127, 89, 34, 230, 166, 126, 164, 205, 47, 113, 245, 71, 45, 90, 44, 2, 17, 0, 0, 0, 14, 180, 148, 216, 156, 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