Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5befd1581fcc9f7b383ac40178d6112c4bba7be49acbd3851b9bc84442f7cd5

Tx prefix hash: 68b90938ea53287d434f0f5f4fbc99a76e88b2849e777b1f53879c23267120f7
Tx public key: 89c2fed627294f7da6ec729a55fb22b5288ecf75629e33c73aff2ec3ebc2cf2b
Timestamp: 1724017175 Timestamp [UCT]: 2024-08-18 21:39:35 Age [y:d:h:m:s]: 00:145:08:40:09
Block: 1090864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103984 RingCT/type: yes/0
Extra: 0189c2fed627294f7da6ec729a55fb22b5288ecf75629e33c73aff2ec3ebc2cf2b02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdbb492d46aa2b56cd9e635ea74fb4bbf695021216af7f9c832c86c32943fa2b 0.600000000000 1565489 of 15

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": 1090874, "vin": [ { "gen": { "height": 1090864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdbb492d46aa2b56cd9e635ea74fb4bbf695021216af7f9c832c86c32943fa2b" } } ], "extra": [ 1, 137, 194, 254, 214, 39, 41, 79, 125, 166, 236, 114, 154, 85, 251, 34, 181, 40, 142, 207, 117, 98, 158, 51, 199, 58, 255, 46, 195, 235, 194, 207, 43, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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