Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11ebb32d4db05ff072d8618406c7f4f6aceb55468d3077517721d1f074c882b3

Tx prefix hash: 59dd8f217eb2e20ba85e0ca746577c9baaf90f65c295ea3a8f5f867e0aaa940a
Tx public key: f662084460c2ca3597ab7e8b428b379509922bd1d80b344085e535b94ba9f3e0
Timestamp: 1634976788 Timestamp [UCT]: 2021-10-23 08:13:08 Age [y:d:h:m:s]: 03:186:11:18:37
Block: 358684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 911395 RingCT/type: yes/0
Extra: 01f662084460c2ca3597ab7e8b428b379509922bd1d80b344085e535b94ba9f3e002110000000cf29d7abf000000000000000000

1 output(s) for total of 39.767786821000 dcy

stealth address amount amount idx
00: a735eefb4fcb0e09f5d56c281c37ec8f6736887110af47c032c25ad54e7a29b6 39.767786821000 730739 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": 358694, "vin": [ { "gen": { "height": 358684 } } ], "vout": [ { "amount": 39767786821, "target": { "key": "a735eefb4fcb0e09f5d56c281c37ec8f6736887110af47c032c25ad54e7a29b6" } } ], "extra": [ 1, 246, 98, 8, 68, 96, 194, 202, 53, 151, 171, 126, 139, 66, 139, 55, 149, 9, 146, 43, 209, 216, 11, 52, 64, 133, 229, 53, 185, 75, 169, 243, 224, 2, 17, 0, 0, 0, 12, 242, 157, 122, 191, 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