Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c0edac792759cdb4a24d02dd14572abb9d0f5b8b02ebfffb189a56a0cd82d47

Tx prefix hash: aa35ae3ced7825a26cfa25c4e61a52c885aa6226870442bdc8b049d70e57f42e
Tx public key: cf777a7c83c662d937eb6e1cbfeee5cb2b447634d9f1f32767b505458489ebf9
Timestamp: 1694820342 Timestamp [UCT]: 2023-09-15 23:25:42 Age [y:d:h:m:s]: 01:343:02:36:46
Block: 848990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504114 RingCT/type: yes/0
Extra: 01cf777a7c83c662d937eb6e1cbfeee5cb2b447634d9f1f32767b505458489ebf902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.943938621000 dcy

stealth address amount amount idx
00: 841a6ea8ca6a34825e05f274f7692755ae3fd6b510c30407b1d52c43d1e25c24 0.943938621000 1302626 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": 849000, "vin": [ { "gen": { "height": 848990 } } ], "vout": [ { "amount": 943938621, "target": { "key": "841a6ea8ca6a34825e05f274f7692755ae3fd6b510c30407b1d52c43d1e25c24" } } ], "extra": [ 1, 207, 119, 122, 124, 131, 198, 98, 217, 55, 235, 110, 28, 191, 238, 229, 203, 43, 68, 118, 52, 217, 241, 243, 39, 103, 181, 5, 69, 132, 137, 235, 249, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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